Skip to main content
Version: 8.4.08.4

ClientTrading

#Message NameDescription
2270ExternAggGroupReport
3985SpdrAccntCancelRecords inserted into this table will result in the cancellation of all active/cancelable orders for the indicated SpiderRock trading accnt.
1450SpdrAwayExecutionSpdrAwayExecution records are published by ToolServers, SRSE, and FIX drop recv gateways. They are consumed by AwayExecutionMarkupServer which, in turn, publishes corresponding SpdrParentExecution records, including M1 and M10 updates.
3990SpdrBrokerCancelRecords inserted into this table causes the corresponding parent broker to cancel the current underlying parent order if active and cancellable.
4025SpdrMLegBrkrEventSpdrMLegBrkrEvent records are published when a new or clx/replace parent order arrives causes a broker to beging working and again when a parent order terminates and the underlying broker stops working. The initial version contains state and market data from just after the initial risk check and first attempt at generating child orders.
4030SpdrMLegBrkrStateSpdrMLegBrkrState records are published by execution engines and describe the current state of a broker that is managing a SpiderRock parent order. These records include a description of the active child orders managed by the broker. Records are updated whenever a child order changes and also at other times but are not completely live and may not always reflect current market data or limit levels for working orders.
4065SpdrParentBrkrEventSpdrParentBrkrEvent records are published when a new or cxl/replace parent order arrives causes a broker to begin working and again when a parent order terminates and the underlying broker stops working. The initial version contains state and market data from just after the initial risk check and first attempt at generating child orders.
4070SpdrParentBrkrStateSpdrParentBrkrState records are created/published by SpiderRock Execution Engines. Each record describes the current state of one (or more) parent orders. If a parent order is canceled/replaced then entire chain is represented by a single broker state record.
4080SpdrParentCancelRecords inserted into this table causes the corresponding parent order to be cancelled if it is active and cancellable.

Either put in a custom datasource or deprecate from SRSE (Natively not allowed to be modified via SRSE)
4085SpdrParentExecutionSpdrParentExecution records are published every time a parent order execution is received. They also update as additional post execution mark information is available at F+1m and F+10m.
4090SpdrParentLimitSpdrParentLimit records are supplied by clients (via SRSE) for use with parent orders having orderLimitType=Aux. This table can be updated either before or after a parent order begins working and will influence the limit(s) used when working child orders. Updates to this table do not constitute cancel/replace operations for the parent order.
4095SpdrParentOrderSpdrParentOrder records are visible in SRSE immediately after receipt. Parent orders received via FIX, SRSE or SpiderRock GUI tools, or 3rd party vendor systems are all visible in this table.

Parent orders can be for stocks, futures, options or spreads. And they can be one-sided (agency) or two-sided (facilitation) orders. Parent order records should be immutable and not update.

SpdrParentOrder records are published to the SpiderRock elatic cluster on arrival.
1467SpdrRiskGroupCancelRecords inserted into this table causes the corresponding parent broker to cancel the current underlying parent order if active and cancellable.
3480ToolCompositeExecution